X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C91F2B.50A6B335@onstor-exch02.onstor.net>; Thu, 25 Sep 2008 09:25:25 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C91F2B.50A6B335"
Content-class: urn:content-classes:message
Subject: RE: meek option to delete snapshots
Date: Thu, 25 Sep 2008 09:25:21 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0BBAE0A2@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0BBADF98@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: meek option to delete snapshots
Thread-Index: Acke1tcPtbDXgoVOQ/6B+kHJ6FV8KgAC20UgABDWXgA=
References: <2779531E7C760D4491C96305019FEEB514ACB0D252@exch1.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0BBADF98@onstor-exch02.onstor.net>
From: "Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>
To: "Neil Cook" <neil.cook@onstor.com>,
	"Shin Irie" <shin.irie@onstor.com>,
	"dl-cstech" <dl-cstech@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C91F2B.50A6B335
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

When filesystem detects corruption, we have mainly two choices -

1.	Wait for the user to repair the volume.
2.	Initiate the eek repair immediately (MEEK)

It is debatable which approach is better. Probably, we can provide some
ways to choose this behavior per volume.

There are some concerns when we allow operating on a corrupt filesystem
before repair:

1.	Modify operations on a corrupt filesystem may further damage the
filesystem.
2.	No operation is guaranteed to produce the expected result on a
corrupt filesystem (including reads).
3.	MEEK is triggered after volume exceptions or log replay
failures.  MEEK cannot be skipped after log replay failures.  If we skip
MEEK after volume exceptions, the filesystem may throw volume exceptions
in a loop (this was one of the biggest complaints a while back).  Some
of the corruptions may cause system panics as well (causing downtime for
all the filesystems served by the filer or cluster).

There are ways to abort MEEK.  Prior to 3.2.0.4, this was a bit involved
though.  The user can always choose to abort the MEEK and continue
operating on corrupt filesystems and schedule offline eek repair at his
convenience.  Offline eek provides options to remove all the snapshots.
Skipping snapshots during eek is not advised since the filesystem will
not be completely consistent.

It is highly recommended to upgrade to newer releases, run eek in
verification mode on a newly created snapshot (which does not block
filesystem services) and schedule offline eek repair if the filesystem
has inconsistencies (in limited cases online eek repair will suffice).
This is very important especially when upgrading from releases older
than 3.1.

Regards,
Jobi

_____________________________________________
From: Neil Cook=20
Sent: Thursday, September 25, 2008 1:01 AM
To: Shin Irie; dl-cstech
Subject: RE: meek option to delete snapshots

How about meek just checks the live filesystem, snap 0, and then gives
us a warning saying snapshots should be checked in the elog? When meek
has kicked off on large volumes with a lot of snapshots it tends to be
aborted and then a manual eek run on the live filesystem to get the
customer back up and running as quickly as possible.This may include
deleting the snapshots at this point or later once the volume is online.
This is mainly due to time and the lack of feedback in elogs when a meek
is running. As I've said before we should changed the volume status to
'FSCK' (and perhaps 'aFSCK' if it were a meek to show the difference)
instead of paused this gives the customer instant feedback on what is
happening with there volume. Currently if a customer rings in and says
the volume is in a paused state we have to check the logs before we know
exactly what is happening with the volume.=20

Meek is a great function however customers tend to want to get there
data back as quick as possible, I know of very few customers (OK none!)
that are happy for there volumes to be offline for any length of time. I
do think we could do both really and have some meek settings that allow
it to check all of volume including snapshots, to check just the live
filesystem, check the live filesystem and delete all snapshots and the
fourth option would be to turn off meek altogether. This would be best
set on a per volume or per VSVR basis. The only issue I see with
deleting snapshots is when the volume is a mirror source, perhaps we
could allow for intelligence of the setting not to allow option 3 if the
volume is part of a mirror. There is an argument to say that the mirror
is then corrupt but at least most of the data will be on the target and
in most instances the mirror continues. Once the meek is complete we can
advise about recreating the mirror.

Regards,
=20

Neil Cook
Senior Technical Support &=20
Escalations Engineer

ONStor, Inc.
Office:   +44 1189 635 866
Mobile: +44 7887 685 582=20
=20
HYPERLINK "mailto:neil.cook@onstor.com"neil.cook@onstor.com
HYPERLINK "http://www.onstor.com/"http://www.onstor.com
=20
=20
EMEA Support Line
Phone:   +44 (0) 8707 347 448
Email:    HYPERLINK "mailto:Support@ONStor.com"Support@ONStor.com
Web:      HYPERLINK "http://support.onstor.com/"Support.ONStor.com

_____________________________________________
From: Shin Irie=20
Sent: 25 September 2008 07:21
To: dl-cstech
Subject: meek option to delete snapshots

Meek with 3.1.0.7 or greater checks snapshots too.  This means it will
take very long to complete if there are many snapshots on the volume.
Actually, I have a customer who had a volume exception and meek took 3
days.  The volume has 10 snapshots: 8 hourly and 2 daily (this is a
default setting).  If there were no snapshots, meek would have completed
in 6 hours.

How about adding an option to delete all snapshots before a meek run?
It can be up to the customer to turn it on depending on which they want,
shorter meek time or holding all snapshots.  Or it can be a hidden
option and we (CS or Dev, or whatever) decide to turn it on depending
various situations such as business with the customer etc.



--
Irie


No virus found in this incoming message.
Checked by AVG.=20
Version: 7.5.524 / Virus Database: 270.7.2/1689 - Release Date:
24/09/2008 18:51
=20

No virus found in this outgoing message.
Checked by AVG.=20
Version: 7.5.524 / Virus Database: 270.7.2/1689 - Release Date:
24/09/2008 18:51
=20

------_=_NextPart_001_01C91F2B.50A6B335
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: meek option to delete snapshots</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">When filesystem detects =
corruption, we have</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">mainly</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">two =
choices -</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Wait for the user to =
repair the volume.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Initiate the eek repair =
immediately (MEEK)</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">It is debatable</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">which</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial"> approach is better.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">Probably, we can provide some ways to choose =
this behavior per volume.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">T</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">here</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">are</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">some concerns when we allow operating on a =
corrupt filesystem</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> before =
repair</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">Modify operations on a corrupt filesystem may =
further damage the filesystem.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">No operation is</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">guaranteed</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial"> to</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">produce the expected result on a corrupt =
filesystem</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> =
(including reads).</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT> <FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">MEEK is triggered after volume =
exception</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">s</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> or log =
replay failure</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">s</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">.&nbsp; =
MEEK cannot be skipped after log replay failure</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">s</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">.&nbsp; =
If we skip MEEK after volume exception</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">s</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">, the =
filesystem may throw volume exceptions in a loop (this was =
one</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">of the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">biggest complaints a while =
back).</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">&nbsp; =
Some of the corruptions may cause system panics as well (causing =
downtime for all the filesystems served by the filer</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial"> or cluster</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">).</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">There are ways to abort MEEK.&nbsp; Prior to 3.2.0.4, =
this was a bit involved though.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">&nbsp; The user can always</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">choose</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">to abort</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">MEEK and continue operating on corrupt =
filesystems</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">and</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> schedule =
offline eek repair at his convenience.&nbsp; Offline eek provides =
options to remove all the snapshots.&nbsp; Skipping snapshots =
during</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">eek is not advised since =
the filesystem will not be completely consistent.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">It is highly recommended to upgrade to</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">newer releases</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">, run eek in verification mode on a newly =
created snapshot (which does not block</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">filesystem services) and schedule offline eek =
repair if the filesystem has inconsistencies (in limited cases online =
eek repair will suffice).</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">&nbsp; =
This is very important especially when upgrading from releases older =
than 3.1.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Jobi</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Neil Cook<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Thursday, September 25, =
2008 1:01 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Shin Irie; dl-cstech<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: meek option to delete snapshots</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">How about meek just checks the =
live filesystem, snap 0, and then gives us a warning saying snapshots =
should be checked in the elog? When meek has kicked off on large volumes =
with a lot of snapshots it tends to be aborted and then a manual eek run =
on the live filesystem to get the customer back up and running as =
quickly as possible.This may include deleting the snapshots at this =
point or later once the volume is online. This is mainly due to time and =
the lack of feedback in elogs when a meek is running. As I&#8217;ve said =
before we should changed the volume status to &#8216;FSCK&#8217; (and =
perhaps &#8216;aFSCK&#8217; if it were a meek to show the difference) =
instead of paused this gives the customer instant feedback on what is =
happening with there volume. Currently if a customer rings in and says =
the volume is in a paused state we have to check the logs before we know =
exactly what is happening with the volume. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Meek is a great function however customers tend to want =
to get there data back as quick as possible, I know of very few =
customers (OK none!) that are happy for there volumes to be offline for =
any length of time. I do think we could do both really and have some =
meek settings that allow it to check all of volume including snapshots, =
to check just the live filesystem, check the live filesystem and delete =
all snapshots and the fourth option would be to turn off meek =
altogether. This would be best set on a per volume or per VSVR basis. =
The only issue I see with deleting snapshots is when the volume is a =
mirror source, perhaps we could allow for intelligence of the setting =
not to allow option 3 if the volume is part of a mirror. There is an =
argument to say that the mirror is then corrupt but at least most of the =
data will be on the target and in most instances the mirror continues. =
Once the meek is complete we can advise about recreating the =
mirror.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><A =
NAME=3D""><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">Regards,</FONT></SPAN></A></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" FACE=3D"Arial">Neil =
Cook</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><BR>
<FONT COLOR=3D"#000080" FACE=3D"Arial">Senior Technical Support &amp; =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">Escalations Engineer<BR>
<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" FACE=3D"Arial">ONStor, =
Inc.</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><BR>
</SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" FACE=3D"Arial">Office:</FONT></SPAN></B><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">&nbsp;&nbsp; +44 1189 635 866<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">Mobile:</FONT></SPAN></B><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial"> +44 7887 685 582 </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">&nbsp;</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" FACE=3D"Arial">HYPERLINK &quot;<A =
HREF=3D"mailto:ne">mailto:ne</A></FONT></SPAN></B><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" =
FACE=3D"Arial">il.cook@onstor.com&quot;</FONT></SPAN></B><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"en-us"></SPAN></B><SPAN =
LANG=3D"en-us"><B><U></U></B></SPAN><B><U><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" =
FACE=3D"Arial">neil.cook@onstor.com</FONT></SPAN></U></B><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><BR>
</SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" FACE=3D"Arial">HYPERLINK &quot;<A =
HREF=3D"http://www">http://www</A></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">.onstor.com/&quot;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><B><U></U></B></SPAN><B><U><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" FACE=3D"Arial"><A =
HREF=3D"http://www.onstor.com">http://www.onstor.com</A></FONT></SPAN></U=
></B><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">&nbsp;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" FACE=3D"Arial">EMEA Support =
Line</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">Phone:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" FACE=3D"Arial">&nbsp;&nbsp; +44 =
(0) 8707 347 448</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">Email:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
FACE=3D"Arial">HYPERLINK &quot;mailto:</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">Support@ONStor.com&quot;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><U></U></SPAN><U><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" =
FACE=3D"Arial">Support@ONStor.com</FONT></SPAN></U><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B></B></SPAN><B><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">Web:</FONT></SPAN></B><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
FACE=3D"Arial">HYPERLINK &quot;<A =
HREF=3D"http://">http://</A></FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
FACE=3D"Arial">support.onstor.com/&quot;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><U></U></SPAN><U><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#0000FF" =
FACE=3D"Arial">Support.ONStor.com</FONT></SPAN></U><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Shin Irie<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> 25 September 2008 =
07:21<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> dl-cstech<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> meek option to delete snapshots</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Meek with 3.1.0.7 or greater checks snapshots =
too.&nbsp; This means it will take very long to complete if there are =
many snapshots on the volume.&nbsp; Actually, I have a customer who had =
a volume exception and meek took 3 days.&nbsp; The volume has 10 =
snapshots: 8 hourly and 2 daily (this is a default setting).&nbsp; If =
there were no snapshots, meek would have completed in 6 =
hours.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">How =
about adding an option to delete all snapshots before a meek run?&nbsp; =
It can be up to the customer to turn it on depending on which they want, =
shorter meek time or holding all snapshots.&nbsp; Or it can be a hidden =
option and we (CS or Dev, or whatever) decide to turn it on depending =
various situations such as business with the customer =
etc.</FONT></SPAN></P>
<BR>
<BR>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">--</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Irie</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><BR>
<FONT SIZE=3D2 FACE=3D"Arial">No virus found in this incoming =
message.<BR>
Checked by AVG.<BR>
Version: 7.5.524 / Virus Database: 270.7.2/1689 - Release Date: =
24/09/2008 18:51<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><BR>
<FONT SIZE=3D2>No virus found in this outgoing message.<BR>
Checked by AVG.<BR>
Version: 7.5.524 / Virus Database: 270.7.2/1689 - Release Date: =
24/09/2008 18:51<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;</SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C91F2B.50A6B335--
